System and Method for Content Protection on a Computing Device

ABSTRACT

Systems and methods for handling user interface field data. A system and method can be configured to receive input which indicates that the mobile device is to enter into a protected mode. Data associated with fields displayed on a user interface are stored in a secure form on the mobile device. After the mobile device leaves the protected mode, the stored user interface filed data is accessed and used to populate one or more user interface fields with the accessed user interface field data for display to a user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 11/118,133 filed Apr. 29, 2005, by Neil P. Adams, et al. entitled “System and Method for Content Protection on a Computing Device”, (11924-US-PAT; 4214-25901) which claims priority to U.S. Provisional Patent Application No. 60/567,080, filed Apr. 30, 2004, by Neil P. Adams, et al. entitled “System and Method for Content Protection on a Computing Device”, (11924-US-PRV; 4214-25900) which are incorporated by reference herein as if reproduced in their entirety.

TECHNICAL FIELD AND BACKGROUND

This document relates generally to the field of communications, and in particular to protecting content on computing devices.

Mobile devices contain user interfaces for users to interact with the mobile device. Users can both view and input data through data fields provided through the mobile devices' user interfaces. However, a mobile device's field data may not be able to be handled effectively and/or efficiently when the mobile device is entering or has entered a protected mode (e.g., a locked state).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an example communication system in which a wireless communication device may be used.

FIG. 2 is a block diagram of a further example communication system including multiple networks and multiple mobile communication devices.

FIG. 3 is a block diagram depicting user interface fields that appear on user interface screen(s) of a mobile device.

FIGS. 4 and 5 are block diagrams depicting protection of content located on user interface screens.

FIG. 6 is a flowchart illustrating an example of an operational scenario for handling user field data on a mobile device.

FIGS. 7 and 8 are flowcharts illustrating an example of an operational scenario for creating encryptable fields in order to protect content.

FIG. 9 is user interface screen displayed to a user of a mobile device.

FIG. 10 is a block diagram of an example mobile device.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overview of an example communication system in which a wireless communication device may be used. One skilled in the art will appreciate that there may be hundreds of different topologies, but the system shown in FIG. 1 helps demonstrate the operation of the encoded message processing systems and methods described in the present application. There may also be many message senders and recipients. The simple system shown in FIG. 1 is for illustrative purposes only, and shows perhaps the most prevalent Internet e-mail environment where security is not generally used.

FIG. 1 shows an e-mail sender 10, the Internet 20, a message server system 40, a wireless gateway 85, wireless infrastructure 90, a wireless network 105 and a mobile communication device 100.

An e-mail sender system 10 may, for example, be connected to an ISP (Internet Service Provider) on which a user of the system 10 has an account, located within a company, possibly connected to a local area network (LAN), and connected to the Internet 20, or connected to the Internet 20 through a large ASP (application service provider) such as America Online (AOL). Those skilled in the art will appreciate that the systems shown in FIG. 1 may instead be connected to a wide area network (WAN) other than the Internet, although e-mail transfers are commonly accomplished through Internet-connected arrangements as shown in FIG. 1.

The message server 40 may be implemented, for example, on a network computer within the firewall of a corporation, a computer within an ISP or ASP system or the like, and acts as the main interface for e-mail exchange over the Internet 20. Although other messaging systems might not require a message server system 40, a mobile device 100 configured for receiving and possibly sending e-mail will normally be associated with an account on a message server. Perhaps the two most common message servers are Microsoft Exchange™ and Lotus Domino™. These products are often used in conjunction with Internet mail routers that route and deliver mail. These intermediate components are not shown in FIG. 1, as they do not directly play a role in the secure message processing described below. Message servers such as server 40 typically extend beyond just e-mail sending and receiving; they also include dynamic database storage engines that have predefined database formats for data like calendars, to-do lists, task lists, e-mail and documentation.

The wireless gateway 85 and infrastructure 90 provide a link between the Internet 20 and wireless network 105. The wireless infrastructure 90 determines the most likely network for locating a given user and tracks the user as they roam between countries or networks. A message is then delivered to the mobile device 100 via wireless transmission, typically at a radio frequency (RF), from a base station in the wireless network 105 to the mobile device 100. The particular network 105 may be virtually any wireless network over which messages may be exchanged with a mobile communication device.

As shown in FIG. 1, a composed e-mail message 15 is sent by the e-mail sender 10, located somewhere on the Internet 20. This message 15 is normally fully in the clear and uses traditional Simple Mail Transfer Protocol (SMTP), RFC822 headers and Multipurpose Internet Mail Extension (MIME) body parts to define the format of the mail message. These techniques are all well known to those skilled in the art. The message 15 arrives at the message server 40 and is normally stored in a message store. Most known messaging systems support a so-called “pull” message access scheme, wherein the mobile device 100 must request that stored messages be forwarded by the message server to the mobile device 100. Some systems provide for automatic routing of such messages which are addressed using a specific e-mail address associated with the mobile device 100. In a preferred embodiment described in further detail below, messages addressed to a message server account associated with a host system such as a home computer or office computer which belongs to the user of a mobile device 100 are redirected from the message server 40 to the mobile device 100 as they are received.

Regardless of the specific mechanism controlling the forwarding of messages to the mobile device 100, the message 15, or possibly a translated or reformatted version thereof, is sent to the wireless gateway 85. The wireless infrastructure 90 includes a series of connections to wireless network 105. These connections could be Integrated Services Digital Network (ISDN), Frame Relay or T1 connections using the TCP/IP protocol used throughout the Internet. As used herein, the term “wireless network” is intended to include three different types of networks, those being (1) data-centric wireless networks, (2) voice-centric wireless networks and (3) dual-mode networks that can support both voice and data communications over the same physical base stations. Combined dual-mode networks include, but are not limited to, (1) Code Division Multiple Access (CDMA) networks, (2) the Groupe Special Mobile or the Global System for Mobile Communications (GSM) and the General Packet Radio Service (GPRS) networks, and (3) future third-generation (3G) networks like Enhanced Data-rates for Global Evolution (EDGE) and Universal Mobile Telecommunications Systems (UMTS). Some older examples of data-centric network include the Mobitex™ Radio Network and the DataTAC™ Radio Network. Examples of older voice-centric data networks include Personal Communication Systems (PCS) networks like GSM, and TDMA systems.

FIG. 2 is a block diagram of a further example communication system including multiple networks and multiple mobile communication devices. The system of FIG. 2 is substantially similar to the FIG. 1 system, but includes a host system 30, a redirection program 45, a mobile device cradle 65, a wireless virtual private network (VPN) router 75, an additional wireless network 110 and multiple mobile communication devices 100. As described above in conjunction with FIG. 1, FIG. 2 represents an overview of a sample network topology. Although the encoded message processing systems and methods described herein may be applied to networks having many different topologies, the network of FIG. 2 is useful in understanding an automatic e-mail redirection system mentioned briefly above.

The central host system 30 will typically be a corporate office or other LAN, but may instead be a home office computer or some other private system where mail messages are being exchanged. Within the host system 30 is the message server 40, running on some computer within the firewall of the host system, that acts as the main interface for the host system to exchange e-mail with the Internet 20. In the system of FIG. 2, the redirection program 45 enables redirection of data items from the server 40 to a mobile communication device 100. Although the redirection program 45 is shown to reside on the same machine as the message server 40 for ease of presentation, there is no requirement that it must reside on the message server. The redirection program 45 and the message server 40 are designed to co-operate and interact to allow the pushing of information to mobile devices 100. In this installation, the redirection program 45 takes confidential and non-confidential corporate information for a specific user and redirects it out through the corporate firewall to mobile devices 100. A more detailed description of the redirection software 45 may be found in the commonly assigned U.S. Pat. No. 6,219,694 (“the '694 patent”), entitled “System and Method for Pushing Information From A Host System To A Mobile Data Communication Device Having A Shared Electronic Address”, and issued to the assignee of the instant application on Apr. 17, 2001, which is hereby incorporated into the present application by reference. This push technique may use a wireless friendly encoding, compression and encryption technique to deliver all information to a mobile device, thus effectively extending the security firewall to include each mobile device 100 associated with the host system 30.

As shown in FIG. 2, there may be many alternative paths for getting information to the mobile device 100. One method for loading information onto the mobile device 100 is through a port designated 50, using a device cradle 65. This method tends to be useful for bulk information updates often performed at initialization of a mobile device 100 with the host system 30 or a computer 35 within the system 30. The other main method for data exchange is over-the-air using wireless networks to deliver the information. As shown in FIG. 2, this may be accomplished through a wireless VPN router 75 or through a traditional Internet connection 95 to a wireless gateway 85 and a wireless infrastructure 90, as described above. The concept of a wireless VPN router 75 is new in the wireless industry and implies that a VPN connection could be established directly through a specific wireless network 110 to a mobile device 100 via connection 115. The possibility of using a wireless VPN router 75 has only recently been available and could be used when the new Internet Protocol (IP) Version 6 (IPV6) arrives into IP-based wireless networks. This new protocol will provide enough IP addresses to dedicate an IP address to every mobile device 100 and thus make it possible to push information to a mobile device 100 at any time. A principal advantage of using this wireless VPN router 75 is that it could be an off-the-shelf VPN component, thus it would not require a separate wireless gateway 85 and wireless infrastructure 90 to be used. A VPN connection would preferably be a Transmission Control Protocol (TCP)/IP or User Datagram Protocol (UDP)/IP connection to deliver the messages directly to the mobile device 100. If a wireless VPN 75 is not available then a link 95 to the Internet 20 is the most common connection mechanism available and has been described above.

In the automatic redirection system of FIG. 2, a composed e-mail message 15 leaving the e-mail sender 10 arrives at the message server 40 and is redirected by the redirection program 45 to the mobile device 100. As this redirection takes place the message 15 is re-enveloped, as indicated at 80, and a possibly proprietary compression and encryption algorithm can then be applied to the original message 15. In this way, messages being read on the mobile device 100 are no less secure than if they were read on a desktop workstation such as 35 within the firewall. All messages exchanged between the redirection program 45 and the mobile device 100 preferably use this message repackaging technique. Another goal of this outer envelope is to maintain the addressing information of the original message except the sender's and the receiver's address. This allows reply messages to reach the appropriate destination, and also allows the “from” field to reflect the mobile user's desktop address. Using the user's e-mail address from the mobile device 100 allows the received message to appear as though the message originated from the user's desktop system 35 rather than the mobile device 100.

With reference back to the port 50 and cradle 65 connectivity to the mobile device 100, this connection path offers many advantages for enabling one-time data exchange of large items. For those skilled in the art of personal digital assistants (PDAs) and synchronization, the most common data exchanged over this link is Personal Information Management (PIM) data 55. When exchanged for the first time this data tends to be large in quantity, bulky in nature and requires a large bandwidth to get loaded onto the mobile device 100 where it can be used on the road. This serial link may also be used for other purposes, including setting up a private security key 111 such as an S/MIME or PGP specific private key, the Certificate (Cert) of the user and their Certificate Revocation Lists (CRLs) 60. The private key is preferably exchanged so that the desktop 35 and mobile device 100 share one personality and one method for accessing all mail. The Cert and CRLs are normally exchanged over such a link because they represent a large amount of the data that is required by the device for S/MIME, PGP and other public key security methods.

FIG. 3 depicts a mobile device 100 that is in an unlocked state. The mobile device 100 provides one or more user interface screens 200 through which to interact with a user 230 of the device 100. Content in the form of user field data 220 is provided by the user 230 to fields 210 that appear on the user interface screens 200. An example of user field data 210 can include text or numbers (or combinations thereof) entered by a user 230 into a device's memo pad application.

It is noted that when the device 100 is unlocked, the mobile device 100 may keep the device's private key decrypted in a temporary buffer. The mobile device 100 goes into a secure mode when the mobile device 100 enters into a locked state. In such a state, the mobile device 100 can erase the temporary buffer that holds the private key.

The device becomes completely secure when it is locked. An indication to the user that the device has become completely secure can be provided by showing a lock icon on an information banner of the mobile device 100. The mobile device 100 can be configured to display this icon as soon as possible after the device enters a locked state so that the user can see that content protection is working. However, the lock icon may not appear if the device locks while the user is viewing or editing PIM data, or viewing an e-mail message, or composing an e-mail message (including forwarding and replying to messages). This can arise because some of the user's data is stored on screens and is therefore not protected by content protection.

FIG. 4 depicts a system that addresses such situations by providing content protection for data contained in user interface fields 210 for when the mobile device 100 enters into a locked state. The content protection depicted in FIG. 4 provides a secure mode for the device 100 wherein the user-entered data is stored on the device 100 (e.g., in flash memory and/or RAM) in an encrypted form.

For example, user field data 300 is provided to an encryption software module 310 which places the user field data 300 in an encrypted form 320. Such protection counters attacks where an adversary steals a device 100, opens the device 100 and uses JTag or similar methods to read the data directly from the device's flash chip.

With reference to FIG. 5, when a mobile device 100 has become unlocked, the encrypted user field data is decrypted by decryption software module 350, thereby reacquiring the user field data 300. The user field data 300 is then used to populate one or more user fields 210 that had appeared on the device's user interface screen(s) 200.

FIG. 6 illustrates an example of an operational scenario for handling user field data. At step 400 of the operational scenario, an indication is received that the mobile device is to enter into a protected mode. User field data that appears on the device's user interface screens are stored in a secure form at step 402.

Later when an indication is received at step 404 that the mobile device is leaving or is no longer in a protected mode, the stored secured user field data is accessed at step 406. The accessed user field data is used to repopulate at step 408 the user fields that appear on one or more of the user interfaces.

FIGS. 7 and 8 illustrate an example of an operational scenario for creating encryptable fields in order to protect content. With reference to FIG. 7, a user enters content into one or more fields on a user interface screen at step 500. The user could also take the default values of one or more fields. At step 502, the mobile device enters into a lock mode. The device could have entered the lock mode for many different reasons, such as the mobile device automatically entering the lock mode after a certain period of user inactivity, or the mobile device enters the lock mode because of user input.

In this particular operational scenario, when the device is locked, the device automatically encrypts the fields' contents at step 504 and stores at step 506 the encrypted data in a data store 508 (e.g., in a member variable). The plain text is cleared from the screen at step 510. Processing for this operational scenario continues at step 514 as indicated by the continuation marker 512.

With reference to FIG. 8, when the device unlocks at step 514, the data in the data store 508 is accessed at step 516 and decrypted 518. The decrypted field data is then redisplayed on the proper screens. Through such an approach in this operational scenario, the user's data can be protected when the device is locked. This also allows, among other things, that when the user unlocks their device they are returned to the same state (e.g., same or substantially similar screen display) that they were before the device was locked.

It should be understood that the steps and the order of the steps described in this operational scenario may be altered, modified and/or augmented and still achieve the desired outcome. For example, the operational scenario can also include not having to close an application when the device enters a locked state. As another example, the field data can be secured in many different ways, such as through use of symmetric cryptographic key techniques, asymmetric cryptographic key encryption techniques, or combinations thereof.

FIG. 9 depicts an example of a user interface screen 550 that could be displayed to a user of a mobile device. The user interface screen 550 of the example is a screen containing task PIM fields for display to the user. The user interface screen 550 contains a task name field 552, a task status field 554, a task priority field 556, a task due date field 558, and a task notes field 560. A task screen can have more or less fields than what is shown in FIG. 9.

One or more of the fields (552, 554, 556, 558, 560) may have default values already in the field value entry region. For example, the task priority field 556 may be pre-populated with a “normal” task priority value. A user can elect to change a default value if so desired.

If the mobile device enters a lock mode, then the values appearing in the fields (552, 554, 556, 558, 560) will be stored in a secure form and used after the mobile device is unlocked to repopulate the fields (552, 554, 556, 558, 560) with the values. The mobile device can be configured to automatically display the user interface screen 550 with the values after the mobile device is unlocked.

The systems and methods disclosed herein are presented only by way of example and are not meant to limit the scope of the invention. Other variations of the systems and methods described above will be apparent to those skilled in the art and as such are considered to be within the scope of the invention. As an example, a system and method can be configured to receive input which indicates that the mobile device is to enter into a protected mode. Data associated with fields displayed on a user interface are stored in a secure manner on the mobile device. This could include that when a device is placed into a protected mode (e.g., a locked state), data in the device's user interface fields is stored in an encrypted form. After the mobile device leaves the protected mode, the stored user interface field data is accessed and used to populate one or more user interface fields with the accessed user interface field data for display to a user.

As another example, a system and method can be configured for operation upon a mobile device that is capable of displaying interfaces to a user. Input is received which indicates that the mobile device is to enter into a protected mode. Data associated with fields displayed on a user interface is encrypted and stored in a data store. After the mobile device leaves the protected mode, the stored encrypted user interface field data is decrypted and used to populate one or more user interface fields for display to a user.

As another example, a system and method can be configured to include first software instructions that are configured to encrypt data associated with fields displayed on a user interface. The field data encryption is in response to input being received which indicates that the mobile device is to enter into a protected mode. A data store is used to store on the mobile device the encrypted user interface field data. Second software instructions are configured to decrypt the stored encrypted user interface field data in response to the mobile device leaving the protected mode. The one or more user interface fields are populated with the decrypted user interface field data for display to a user.

As yet another example, a content protection scheme can include closing any screens that contain user data. Once the screens are closed the fields can release the plaintext data, which can be garbage collected and zero'ed, thus securing the device. As another example, a content protection scheme could include specifying that the user should return to a main application screen before locking their device.

Still further, the systems and methods disclosed herein may be used with many different computers and devices, such as a wireless mobile communications device shown in FIG. 10. With reference to FIG. 10, the mobile device 100 is a dual-mode mobile device and includes a transceiver 611, a microprocessor 638, a display 622, non-volatile memory 624, random access memory (RAM) 626, one or more auxiliary input/output (I/O) devices 628, a serial port 630, a keyboard 632, a speaker 634, a microphone 636, a short-range wireless communications sub-system 640, and other device sub-systems 642.

The transceiver 611 includes a receiver 612, a transmitter 614, antennas 616 and 618, one or more local oscillators 613, and a digital signal processor (DSP) 620. The antennas 616 and 618 may be antenna elements of a multiple-element antenna, and are preferably embedded antennas. However, the systems and methods described herein are in no way restricted to a particular type of antenna, or even to wireless communication devices.

The mobile device 100 is preferably a two-way communication device having voice and data communication capabilities. Thus, for example, the mobile device 100 may communicate over a voice network, such as any of the analog or digital cellular networks, and may also communicate over a data network. The voice and data networks are depicted in FIG. 10 by the communication tower 619. These voice and data networks may be separate communication networks using separate infrastructure, such as base stations, network controllers, etc., or they may be integrated into a single wireless network.

The transceiver 611 is used to communicate with the network 619, and includes the receiver 612, the transmitter 614, the one or more local oscillators 613 and the DSP 620. The DSP 620 is used to send and receive signals to and from the transceivers 616 and 618, and also provides control information to the receiver 612 and the transmitter 614. If the voice and data communications occur at a single frequency, or closely-spaced sets of frequencies, then a single local oscillator 613 may be used in conjunction with the receiver 612 and the transmitter 614. Alternatively, if different frequencies are utilized for voice communications versus data communications for example, then a plurality of local oscillators 613 can be used to generate a plurality of frequencies corresponding to the voice and data networks 619. Information, which includes both voice and data information, is communicated to and from the transceiver 611 via a link between the DSP 620 and the microprocessor 638.

The detailed design of the transceiver 611, such as frequency band, component selection, power level, etc., will be dependent upon the communication network 619 in which the mobile device 100 is intended to operate. For example, a mobile device 100 intended to operate in a North American market may include a transceiver 611 designed to operate with any of a variety of voice communication networks, such as the Mobitex or DataTAC mobile data communication networks, AMPS, TDMA, CDMA, PCS, etc., whereas a mobile device 100 intended for use in Europe may be configured to operate with the GPRS data communication network and the GSM voice communication network. Other types of data and voice networks, both separate and integrated, may also be utilized with a mobile device 100.

Depending upon the type of network or networks 619, the access requirements for the mobile device 100 may also vary. For example, in the Mobitex and DataTAC data networks, mobile devices are registered on the network using a unique identification number associated with each mobile device. In GPRS data networks, however, network access is associated with a subscriber or user of a mobile device. A GPRS device typically requires a subscriber identity module (“SIM”), which is required in order to operate a mobile device on a GPRS network. Local or non-network communication functions (if any) may be operable, without the SIM device, but a mobile device will be unable to carry out any functions involving communications over the data network 619, other than any legally required operations, such as ‘911’ emergency calling.

After any required network registration or activation procedures have been completed, the mobile device 100 may the send and receive communication signals, including both voice and data signals, over the networks 619. Signals received by the antenna 616 from the communication network 619 are routed to the receiver 612, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog to digital conversion of the received signal allows more complex communication functions, such as digital demodulation and decoding to be performed using the DSP 620. In a similar manner, signals to be transmitted to the network 619 are processed, including modulation and encoding, for example, by the DSP 620 and are then provided to the transmitter 614 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 619 via the antenna 618.

In addition to processing the communication signals, the DSP 620 also provides for transceiver control. For example, the gain levels applied to communication signals in the receiver 612 and the transmitter 614 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 620. Other transceiver control algorithms could also be implemented in the DSP 620 in order to provide more sophisticated control of the transceiver 611.

The microprocessor 638 preferably manages and controls the overall operation of the mobile device 100. Many types of microprocessors or microcontrollers could be used here, or, alternatively, a single DSP 620 could be used to carry out the functions of the microprocessor 638. Low-level communication functions, including at least data and voice communications, are performed through the DSP 620 in the transceiver 611. Other, high-level communication applications, such as a voice communication application 624A, and a data communication application 624B may be stored in the non-volatile memory 624 for execution by the microprocessor 638. For example, the voice communication module 624A may provide a high-level user interface operable to transmit and receive voice calls between the mobile device 100 and a plurality of other voice or dual-mode devices via the network 619. Similarly, the data communication module 624B may provide a high-level user interface operable for sending and receiving data, such as e-mail messages, files, organizer information, short text messages, etc., between the mobile device 100 and a plurality of other data devices via the networks 619.

The microprocessor 638 also interacts with other device subsystems, such as the display 622, the RAM 626, the auxiliary input/output (I/O) subsystems 628, the serial port 630, the keyboard 632, the speaker 634, the microphone 636, the short-range communications subsystem 640 and any other device subsystems generally designated as 642.

Some of the subsystems shown in FIG. 10 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. Notably, some subsystems, such as the keyboard 632 and the display 622 may be used for both communication-related functions, such as entering a text message for transmission over a data communication network, and device-resident functions such as a calculator or task list or other PDA type functions.

Operating system software used by the microprocessor 638 is preferably stored in a persistent store such as non-volatile memory 624. The non-volatile memory 624 may be implemented, for example, as a Flash memory component, or as battery backed-up RAM. In addition to the operating system, which controls low-level functions of the mobile device 610, the non-volatile memory 624 includes a plurality of software modules 624A-624N that can be executed by the microprocessor 638 (and/or the DSP 620), including a voice communication module 624A, a data communication module 624B, and a plurality of other operational modules 624N for carrying out a plurality of other functions. These modules are executed by the microprocessor 638 and provide a high-level interface between a user and the mobile device 100. This interface typically includes a graphical component provided through the display 622, and an input/output component provided through the auxiliary I/O 628, keyboard 632, speaker 634, and microphone 636. The operating system, specific device applications or modules, or parts thereof, may be temporarily loaded into a volatile store, such as RAM 626 for faster operation. Moreover, received communication signals may also be temporarily stored to RAM 626, before permanently writing them to a file system located in a persistent store such as the Flash memory 624.

An exemplary application module 624N that may be loaded onto the mobile device 100 is a personal information manager (PIM) application providing PDA functionality, such as calendar events, appointments, and task items. This module 624N may also interact with the voice communication module 624A for managing phone calls, voice mails, etc., and may also interact with the data communication module for managing e-mail communications and other data transmissions. Alternatively, all of the functionality of the voice communication module 624A and the data communication module 624B may be integrated into the PIM module.

The non-volatile memory 624 preferably also provides a file system to facilitate storage of PIM data items on the device. The PIM application preferably includes the ability to send and receive data items, either by itself, or in conjunction with the voice and data communication modules 624A, 624B, via the wireless networks 619. The PIM data items are preferably seamlessly integrated, synchronized and updated, via the wireless networks 619, with a corresponding set of data items stored or associated with a host computer system, thereby creating a mirrored system for data items associated with a particular user.

Context objects representing at least partially decoded data items, as well as fully decoded data items, are preferably stored on the mobile device 100 in a volatile and non-persistent store such as the RAM 626. Such information may instead be stored in the non-volatile memory 624, for example, when storage intervals are relatively short, such that the information is removed from memory soon after it is stored. However, storage of this information in the RAM 626 or another volatile and non-persistent store is preferred, in order to ensure that the information is erased from memory when the mobile device 100 loses power. This prevents an unauthorized party from obtaining any stored decoded or partially decoded information by removing a memory chip from the mobile device 100, for example.

The mobile device 100 may be manually synchronized with a host system by placing the device 100 in an interface cradle, which couples the serial port 630 of the mobile device 100 to the serial port of a computer system or device. The serial port 630 may also be used to enable a user to set preferences through an external device or software application, or to download other application modules 624N for installation. This wired download path may be used to load an encryption key onto the device, which is a more secure method than exchanging encryption information via the wireless network 619. Interfaces for other wired download paths may be provided in the mobile device 100, in addition to or instead of the serial port 630. For example, a USB port would provide an interface to a similarly equipped personal computer.

Additional application modules 624N may be loaded onto the mobile device 100 through the networks 619, through an auxiliary I/O subsystem 628, through the serial port 630, through the short-range communications subsystem 640, or through any other suitable subsystem 642, and installed by a user in the non-volatile memory 624 or RAM 626. Such flexibility in application installation increases the functionality of the mobile device 100 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the mobile device 100.

When the mobile device 100 is operating in a data communication mode, a received signal, such as a text message or a web page download, is processed by the transceiver module 611 and provided to the microprocessor 638, which preferably further processes the received signal in multiple stages as described above, for eventual output to the display 622, or, alternatively, to an auxiliary I/O device 628. A user of mobile device 100 may also compose data items, such as e-mail messages, using the keyboard 632, which is preferably a complete alphanumeric keyboard laid out in the QWERTY style, although other styles of complete alphanumeric keyboards such as the known DVORAK style may also be used. User input to the mobile device 100 is further enhanced with a plurality of auxiliary I/O devices 628, which may include a thumbwheel input device, a touchpad, a variety of switches, a rocker input switch, etc. The composed data items input by the user may then be transmitted over the communication networks 619 via the transceiver module 611.

When the mobile device 100 is operating in a voice communication mode, the overall operation of the mobile device is substantially similar to the data mode, except that received signals are preferably be output to the speaker 634 and voice signals for transmission are generated by a microphone 636. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on the mobile device 100. Although voice or audio signal output is preferably accomplished primarily through the speaker 634, the display 622 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call related information. For example, the microprocessor 638, in conjunction with the voice communication module and the operating system software, may detect the caller identification information of an incoming voice call and display it on the display 622.

A short-range communications subsystem 640 is also included in the mobile device 100. The subsystem 640 may include an infrared device and associated circuits and components, or a short-range RF communication module such as a Bluetooth™ module or an 802.11 module, for example, to provide for communication with similarly-enabled systems and devices. Those skilled in the art will appreciate that “Bluetooth” and “802.11” refer to sets of specifications, available from the Institute of Electrical and Electronics Engineers, relating to wireless personal area networks and wireless local area networks, respectively.

The systems' and methods' data may be stored in one or more data stores. The data stores can be of many different types of storage devices and programming constructs, such as RAM, ROM, Flash memory, programming data structures, programming variables, etc. It is noted that data structures describe formats for use in organizing and storing data in databases, programs, memory, or other computer-readable media for use by a computer program.

The systems and methods may be provided on many different types of computer-readable media including computer storage mechanisms (e.g., CD-ROM, diskette, RAM, flash memory, computer's hard drive, etc.) that contain instructions for use in execution by a processor to perform the methods' operations and implement the systems described herein.

The computer components, software modules, functions and data structures described herein may be connected directly or indirectly to each other in order to allow the flow of data needed for their operations. It is also noted that a module or processor includes but is not limited to a unit of code that performs a software operation, and can be implemented for example as a subroutine unit of code, or as a software function unit of code, or as an object (as in an object-oriented paradigm), or as an applet, or in a computer script language, or as another type of computer code. 

1. A method of securing a mobile device, the method comprising: receiving input for locking the mobile device; encrypting data entered in at least one field of a user interface, wherein the data is encrypted in response to locking the mobile device; decrypting the encrypted data in response to unlocking the mobile device; and displaying the decrypted data in the at least one field of the user interface, wherein the decrypted data includes content displayed on the user interface prior to locking the mobile device.
 2. The method of claim 1, further comprising storing the encrypted data when the mobile device is locked, wherein the stored encrypted data is cleared from the at least one field of the user interface when the mobile device is locked.
 3. The method of claim 1, wherein the content displayed on the user interface includes data values entered in the at least one field.
 4. The method of claim 1, wherein the data values comprise numeric values, textual values, or combinations thereof.
 5. The method of claim 1, wherein a private key is used to encrypt the data entered in the at least one field of the user interface.
 6. The method of claim 5, wherein the private key is stored in the mobile device.
 7. The method of claim 1, wherein a lock icon is displayed on the user interface when the mobile device is locked.
 8. The method of claim 7, wherein the lock icon is displayed despite the mobile device locking while data in the at least one field was being displayed or edited on the user interface.
 9. The method of claim 1, wherein the encrypted data is stored in an encrypted form in flash memory or random access memory (RAM) of the mobile device.
 10. The method of claim 9, wherein the encrypted form is used to counter an attack on the mobile device in response to an attempt to read data directly from the flash memory or RAM.
 11. The method of claim 6, further comprising erasing the private key when the mobile device is locked.
 12. The method of claim 1, wherein the input for locking the mobile device is generated after a certain period of user interface inactivity.
 13. The method of claim 1, wherein the encrypting and decrypting are performed using at least one of an asymmetric cryptographic technique or a symmetric cryptographic technique.
 14. The method of claim 1, wherein the user interface field data includes PIM (Personal Information Management) data.
 15. The method of claim 1, wherein an application associated with the user interface is not closed when the mobile device is locked.
 16. The method of claim 1, wherein when the mobile device is locked, any screen containing data entered at the user interface is closed, and wherein data contained in any closed screen is encrypted and stored.
 17. The method of claim 1, wherein the mobile device returns to a main application screen before the mobile device is locked.
 18. The method of claim 1, wherein the mobile device comprises a wireless mobile communications device or a personal digital assistant (PDA) that receives messages over a wireless communication network.
 19. At least one computer readable medium comprising instructions executable via a processor of a computing system, wherein executing the instructions by the processor cause the computing system to perform a method comprising: receiving input for locking a mobile device; encrypting data entered in at least one field of a user interface, wherein the data is encrypted in response to locking the mobile device; decrypting the encrypted data in response to unlocking the mobile device; and displaying the decrypted data in the at least one field of the user interface, wherein the decrypted data includes content displayed on the user interface prior to locking the mobile device.
 20. A mobile device comprising: at least one processor capable of: encrypting data entered in at least one field of a user interface, wherein the data is encrypted in response to locking the mobile device; decrypting the encrypted data in response to unlocking the mobile device; and displaying the decrypted data in the at least one field of the user interface, wherein the decrypted data includes content displayed on the user interface prior to locking the mobile device. 